Protected unmanned vehicle delivery receptacle

ABSTRACT

A system for the delivery and secure receipt of packages from unmanned vehicles to improve security and protection of the packages upon delivery. A UAV receptacle provides a water-protected interior to protect a package. The UAV receptacle includes a door in one side that allows a reception tray to extend out and back in, and which locks to protect the package so received. The UAV receptacle detects a drone in proximity. Upon confirming that delivery is for the UAV receptacle, the reception tray extends to a reception position. A sensor detects the package on the reception tray upon delivery from the drone. The reception tray is of a mesh material to reduce water retention. The UAV receptacle retracts the reception tray and closes a door to seal the package within the UAV receptacle. The UAV receptacle may notify user devices that the package has been received.

TECHNICAL FIELD

The present description relates to unmanned vehicles, and morespecifically, to apparatus, systems, methods, and machine-readable mediafor the delivery and secure receipt of packages from unmanned vehiclesto improve security and protection of the packages upon delivery.

BACKGROUND

Delivery of packages by unmanned vehicles, such as unmanned aerialvehicles also referred to at times as “drones,” is a fledgling fieldwith many challenges that remain unsolved in large part. One challengethat has not been adequately resolved is how to ensure safe receipt of apackage to the intended recipient. In practice currently (i.e., innon-drone deliveries), packages must either be signed as accepted by therecipient or are left somewhere at the place of delivery. The former isrequired as the best means of security currently, while the latter oftenis accompanied by attempts to hide the package from notice.

Yet theft of delivered packages remains a problem for existing channelsof delivery, let alone possible forthcoming channels that involvedelivery by drones of some sort. Some have attempted to solve thisproblem with delivery boxes that lock and cannot be accessed without acode. However, these approaches remain subject to other problems, suchas adequate protection of the inside of the delivery box (and, thus,received packages) from inclement weather. Further, the prospect ofthese approaches remain limited in their interfacing with deliverydrones and other systems to ensure the avoidance of unnecessary falsepositives as well as false negatives.

Accordingly, the potential remains for improvements that facilitate thedelivery of packages by unmanned vehicles in a manner that provides (atleast) sufficient security to the packages delivered, better protectionupon delivery from inclement weather, and proper delivery procedures.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is best understood from the following detaileddescription when read with the accompanying figures. In accordance withthe standard practice in the industry, various features are not drawn toscale. In fact, the dimensions of the various features may bearbitrarily increased or reduced for clarity of discussion.

FIG. 1 illustrates an exemplary unmanned vehicle delivery environmentaccording to aspects of the present disclosure.

FIG. 2 is a block diagram of a perspective view of an exemplary unmannedvehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 3A is a block diagram of a side view of an exemplary unmannedvehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 3B is a block diagram of a side view of an exemplary unmannedvehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 3C is a block diagram of a bottom view of an exemplary unmannedvehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 3D is a block diagram of a top view of an exemplary unmannedvehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 4 is a block diagram of a cross-sectional view of an exemplaryunmanned vehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 5A is a block diagram of a front perspective view of an exemplaryunmanned vehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 5B is a block diagram of a front perspective view of an exemplaryexpansion container for an unmanned vehicle delivery receptacleaccording to aspects of the present disclosure.

FIG. 5C is a block diagram of a front perspective view of an exemplaryexpansion container for an unmanned vehicle delivery receptacleaccording to aspects of the present disclosure.

FIG. 5D is a block diagram of a front perspective view of an exemplaryexpansion container coupled to an unmanned vehicle delivery receptacleaccording to aspects of the present disclosure.

FIG. 6 is a block diagram of a control system of an exemplary unmannedvehicle delivery receptacle according to aspects of the presentdisclosure.

FIG. 7 is a block diagram of a user's device in communication with anexemplary unmanned vehicle delivery receptacle according to aspects ofthe present disclosure.

FIG. 8 is a block diagram of a control system of a server incommunication with an exemplary unmanned vehicle delivery receptacleaccording to aspects of the present disclosure.

FIG. 9 is a flow diagram of an exemplary method of operating anexemplary unmanned vehicle delivery receptacle according to aspects ofthe present disclosure.

FIG. 10 is a flow diagram of an exemplary method of unmanned vehicledelivery from a user device perspective according to aspects of thepresent disclosure.

FIG. 11 is a flow diagram of an exemplary method of accounting for anunmanned vehicle delivery according to aspects of the presentdisclosure.

DETAILED DESCRIPTION

All examples and illustrative references are non-limiting and should notbe used to limit the claims to specific implementations and embodimentsdescribed herein and their equivalents. For simplicity, referencenumbers may be repeated between various examples. This repetition is forclarity only and does not dictate a relationship between the respectiveembodiments. Finally, in view of this disclosure, particular featuresdescribed in relation to one aspect or embodiment may be applied toother disclosed aspects or embodiments of the disclosure, even thoughnot specifically shown in the drawings or described in the text.

Various embodiments include systems, methods, and machine-readable mediafor the delivery and secure receipt of packages from unmanned vehiclesto improve security and protection of the packages upon delivery.

According to embodiments of the present disclosure, an unmanned vehicleapparatus (referred to as a UAV receptacle for discussion herein) mayinclude multiple sides formed to provide a water-protected interiordesigned to protect a package. The UAV receptacle may include a door inone side that allows a reception tray to extend out (in a horizontaldirection, perpendicular to a vertical axis of the UAV receptacle) andback in, and which locks to protect the package so received.

In particular, when an unmanned vehicle such as a drone approaches theUAV receptacle to deliver a package, the UAV receptacle may detect thedrone as it approaches a proximity of the UAV receptacle. Uponconfirming that delivery is intended for the UAV receptacle, the UAVreceptacle may cause the reception tray to extend to a receptionposition and, upon detecting by a sensor on the reception tray that apackage has been delivered from the drone, retract the reception trayand close a door to seal the package within the UAV receptacle.

In response thereto, the UAV receptacle may notify one or more userdevices associated with the UAV receptacle that the package has beenreceived. In response, the user may access the contents of the UAVreceptacle by either entering a command to unlock the receptacle via theapp on the user device or via an entry to a user interface on the UAVreceptacle itself. The UAV receptacle may then unlock to allow access tothe package within.

In some embodiments, the UAV receptacle may further be coupled to anexpansion container that may receive and temporarily store multiplepackages for the user. For example, upon receipt of a package, the UAVreceptacle may push the package through an opening connecting the UAVreceptacle interior to an interior of the expansion container, therebyfreeing up the reception tray to be ready to receive another packageshould another delivery be scheduled before the user retrieves the priordelivered package.

As a result, embodiments of the present disclosure improve upon thedelivery of packages by unmanned vehicles in a manner that provides (atleast) sufficient security to the packages delivered, better protectionupon delivery from inclement weather, and proper delivery procedures.

FIG. 1 illustrates an exemplary unmanned vehicle delivery environment100 (also generally referred to as the “environment 100”) according toaspects of the present disclosure. For example, as illustrated, theenvironment 100 may include an exemplary unmanned vehicle deliveryreceptacle 102 (also referred to as a “UAV receptacle 102” or a “dronedrop box 102”), unmanned aerial vehicle 104 (also referred to at timesas a “drone 104,” “UAV 104,” or “unmanned vehicle 104”), package 106(whether a single or multiple packages), building 108 (which may be aresidential building, a commercial building, etc. without departing fromthe scope of the present disclosure), and one or more obstructions 110(illustrated as a tree in FIG. 1, though any of a variety ofobstructions may be contemplated as represented by the tree in FIG. 1 aswell). The environment 100 may include many other aspects, but these arefocused on for purposes of discussing embodiments of the presentdisclosure.

The UAV receptacle 102, according to embodiments of the presentdisclosure, provides a more secure mechanism by which to receivepackages from UAVs 104 in an unmanned vehicle delivery system and willbe discussed in more detail with respect to the other figures herein. Asillustrated, the UAV receptacle 102 is secured on top of a post 103. Thepost 103 may generally be any material and form to offset the UAVreceptacle 102 from the general surface of the ground, and may forexample have a height on the order of 2-4 feet (as just an example). Theheight from the ground may be a variety of heights—typically ofsufficient height to place the UAV receptacle 102 at approximately awaist level of a human user of the UAV receptacle 102.

The UAV receptacle 102 may secure to the post 103, such as by bolting,bonding, welding, gluing, nailing, etc. (or some combination thereof).Further, the post 103 may itself be secured to the ground to preventattempts from stealing the UAV receptacle 102 while still secured to thepost 103. Some examples include bolting the post 103 to a portion ofconcrete, either previously installed (e.g., as part of a patiostructure by a building 108) or installed expressly for the post 103, awooden structure, etc. The UAV receptacle 102 and the post 103 may beprovided in a prepackaged set from a vendor for ease in customerself-installation, or for professional installation.

As illustrated in FIG. 1, the UAV receptacle 102 may be installed with aminimum distance 112 separating the UAV receptacle 102 from anyobstructions 110 and buildings 108. In some examples, the minimumdistance may be on the order of 4 to 8 feet (i.e., a 4 to 8 foot radiusof clearance around the UAV receptacle 102). That is exemplary only. Thesize of the minimum distance 112 may be keyed to the size of the UAVreceptacle 102, which in turn may be keyed to the maximum size ofpackage designed to be received. For example, the UAV receptacle 102 maybe designed to receive a size of package so as to accommodate packagetypes that are most common—e.g., packages on the order of 10-12 inchesin length, height, and/or width. Thus, UAV receptacles 102 dimensionedto receive these smaller packages may have a smaller minimum distance112, while UAV receptacles 102 dimensioned to receive larger averagepackage sizes may have larger minimum distance 112 to neighboringobstructions 110/buildings 108.

The drone 104 illustrated in FIG. 1 is an unmanned aerial vehicleaccording to embodiments of the present disclosure. The drone 104 may beconfigured to carry the package 106 from a source to the targetdestination of the UAV receptacle 102 associated with a user of a systemfor unmanned vehicle delivery. The drone 104 may include circuitry,systems, software, and protocols designed to enable the drone 104 toreceive instruction from a delivery source to receive/retrieve thepackage 106, depart from a delivery source location (e.g., a warehouse,a delivery vehicle that itself may also be manned or unmanned, forexample a truck en route to delivery and dispatched for the so-called“last mile” to the target location of the user), locate the target UAVreceptacle 102 (e.g., by charting and following a course to a registeredbuilding 108 of the user associated with a given package 106), andtravel to the location.

Further, the drone 104 may have one or more communications systemsconfigured to communicate with the communications systems of the UAVreceptacle 102, such as Wi-Fi, Zigbee, near field communications (NFC),Bluetooth, Bluetooth Low Energy, Cellular, etc. (e.g., other types, acombination of types, etc.). Thus, as the drone 104 comes within aproximity of the UAV receptacle 102, the drone 104 and the UAVreceptacle 102 may detect one another and coordinate delivery of thepackage 106 in a secure, safe, and protected manner. For example, insome embodiments the drone 104 may utilize an active RF source torepeatedly interrogate its surroundings. The UAV receptacle 102 may havea passive RF tag to respond to such interrogation and thereby establishcommunication in a manner that conserves power for at least the UAVreceptacle 102 (or, conversely, the UAV receptacle 102 may be the activeinterrogator and the drone 104 the passive listener).

As another example, a back-end control system for the drone 104 may, asa result of tracking the drone 104 during a delivery mission, detectwhen the drone 104 is within a predetermined vicinity of the deliverylocation (i.e., recorded location of the building 108 associated withthe user). As a result of the detection, the back-end control system forthe drone 104 may send a notification (e.g., via one or more networks)to the UAV receptacle 102 to start scanning its environment to detectthe presence of the drone 104 for delivery of a package.

As another alternative or additional example (e.g., in combination withthe above or other proximity detection mechanism), the package 106 mayhave a passive or active RF tag to either be scannable (passive) orinterrogate (active) its environment. As yet another example, inembodiments where the UAV receptacle 102 and the drone 104 areconfigured to detect each other's presence via any of the abovemechanisms (or other similar types), the UAV receptacle 102 may furtherinclude challenge/response protocols to confirm that delivery isintended for that particular UAV receptacle 102 on behalf of a targetuser of the same receptacle.

For example, upon detecting the presence of a drone 104 within a minimumproximity of the UAV receptacle 102, the UAV receptacle 102 mayadditionally send a challenge (e.g., a query or confirmation signal) tothe drone 104 to determine whether the drone 104 is within the proximityto deliver to that particular UAV receptacle 102 or is merely passing byen route to a different delivery location). In response, the drone 104may either transmit a confirm or deny signal, depending on the statuswith respect to the particular user, or provide no answer which may havea default understanding (e.g., no answer means a confirmation or a noanswer means no confirmation, depending upon an agreed protocol). Theseare just a few examples of how the UAV receptacle 102 and the drone 104may establish communication to coordinate delivery of a package 106 tothe UAV receptacle 102 according to embodiments of the presentdisclosure.

Once it is understood that the UAV receptacle 102 is the deviceassociated with the targeted recipient user (e.g., at the properlocation of building 108 associated with the targeted recipient user),and the drone 104 is within the appropriate detected proximity, the UAVreceptacle 102 opens doors (either one or multiple) on a side of thehousing of the UAV receptacle 102. From within the UAV receptacle 102, areception tray is actuated out to a receipt position. The receiptposition is illustrated in an exemplary embodiment in FIG. 4, asdiscussed further below. The reception tray may be designed andconstructed to be a mesh or other material that allows fluids to passthrough, thereby increasing resilience of the UAV receptacle 102 to rainand other inclement weather (and, therefore, better protecting thepackage 106 from that inclement weather).

In particular, by including a reception tray in the UAV receptacle 102that extends out a side of the device, instead of merely opening a spacein the top of the device, precipitation is accorded less opportunity toaccumulate within the UAV receptacle 102 during a delivery run (e.g.,because the precipitation from inclement weather can only enter throughan opening in the side, instead of easier entrance through an opening inthe top of the UAV receptacle 102). Thus, the package 106, as well asthe interior of the UAV receptacle 102, are better protected from anydamaging effects of standing water from precipitation during delivery(aside from any precipitation that accumulates on the package 106 itselfwhile out with the drone 104 for the delivery).

The reception tray may have one or more sensors that detects placementof the package 106 by the drone 104. Further or alternatively, the UAVreceptacle 102 may communicate with the drone 104 and receive anindication from the drone 104 that the package 106 has been delivered(which may function as a confirmation in embodiments where the receptiontray also includes one or more sensors to detect presence of a package106 placed thereon). Once the UAV receptacle 102 receives the package106 (e.g., by a detection signal and/or confirmation signal), thereception tray is actuated back to storage position within the housingof the UAV receptacle 102 and the door is shut again, and in embodimentslocked to protect against theft.

The UAV receptacle 102 may, in addition to one or more communicationssystems that communicate with drones 104, have one or morecommunications systems to communicate with other entities associatedwith the package (which may be the same or different than those tocommunicate with drones 104). For example, the UAV receptacle 102 mayfurther connect to a network system of the user associated with the UAVreceptacle 102 and/or the building 108 to send one or more signals tointerested parties. As a result, the UAV receptacle 102 may generate areceipt signal that is transmitted via the network to one or moreregistering/interested parties. For example, the user may receive anotification from the UAV receptacle 102 according to the receipt signalasserted/generated once the package 106 is received from the drone 104.This may take the form of a direct signal sent from the UAV receptacle102 to a receiving device associated with the user (e.g., direct beingeither to the receiving device, such as a computer, phone, tablet, etc.,without intervening network nodes, or via one or more network nodes butnot requiring a third party server transaction first).

As another example, the delivery entity that has use and/or ownership ofthe drone 104 (e.g., an online retailer), and/or the providing entitythat caused delivery to occur, may also receive a confirmation signalfrom the UAV receptacle 102 confirming that the package 106 has beenreceived (e.g., via the UAV receptacle 102 connecting to the user'snetwork or by the UAV receptacle 102 communicating a confirmation to thedrone 104 before the drone 104 passes out of proximity and/orcommunications range from the UAV receptacle 102). In turn, the deliveryentity may send its own confirmation of delivery to a device associatedwith the user, and/or pay a fractional amount to a distributor of theUAV receptacle 102.

The user of the UAV receptacle 102, having received notification ofreceipt of the package 106 (e.g., from the UAV receptacle 102 via theuser's network and/or from the delivery entity), may then proceed withaccessing the contents of the UAV receptacle 102. For example, the usermay enter a code to a keypad, use a key, submit to a biometric scan,etc. at the UAV receptacle 102. In other embodiments, the user may entera command into a remote device (e.g., via an app of a mobile device) andremotely unlock the UAV receptacle 102 for a person to access thecontents on behalf of the user. Access to the interior of the UAVreceptacle 102 may be via the same door, with the reception trayextending for access, or via a separate access door/hatch on anotherside of the housing of the UAV receptacle 102. In yet other embodiments,an expansion container securely attached to the UAV receptacle 102 maybe accessed via a door to retrieve the package 106.

FIG. 2 provides a more detailed block diagram of an exemplary UAVreceptacle 102, at a top perspective view, according to aspects of thepresent disclosure. The UAV receptacle 102 illustrated in FIG. 2 is anexample of the UAV receptacle introduced in FIG. 1. The UAV receptacle102 includes a housing 202. The housing 202 has a top 201, a bottom 204,a side 206 adjacent to the side 210 having doors 212 a and 212 b,another side 220 adjacent the side 210, and a side 208 opposite the side210. Although illustrated as generally square/cube in form, the UAVreceptacle 102 may assume a variety of dimensions (including roundededges instead of abrupt edges) and shapes including rectangular,ellipsoidal, spherical, etc., without departing from the scope of thepresent disclosure.

On the side 210, the doors 212 a, 212 b are illustrated as beingseparated along a vertical axis extending from the top 201 to the bottom204 of the housing 202. The doors 212 a, 212 b may assume alternativeconfigurations, including being separated along a horizontal axisextending from the sides 206 to 220, and/or have more or fewer totaldoors (e.g., just one door that swings out from the housing 202 whenopening or that slides out with the reception tray, more doors to resultin smaller sizes for each, etc.).

The housing 202 may further include one or more security accessmechanisms 216, illustrated as a keypad in FIG. 2. These may be includedto enable a user of the UAV receptacle 102 to access one or morepackages 106 stored securely within the housing 202 according toembodiments of the present disclosure. Though illustrated on side 206,the security access mechanisms 216 may be included on any other side,whether all together or spread among the sides (and/or top 201), etc.

As further illustrated in FIG. 2, the top 201 of the housing 202 mayinclude a pickup pad 214. The pickup pad 214 may be slightly recessedfrom the rest of the top 201, for example to aid a package 106 frombeing blown from the top 201. In other examples, the pickup pad 214 maybe slightly protruding from the rest of the top 201 for addedprominence, while in other examples the pickup pad 214 is a logicallydefined location on the top 201 that is otherwise substantially flushwith the rest of the top 201 (and, in other embodiments, left off fromthe housing 202). Although illustrated as approximately flat, the top201 may in some embodiments have a curvature extending from an apexaround the center of the top 201 towards lower edges (e.g., anelliptical shape) that allows precipitation to run in many directionsaway from the apex center. Further, the pickup pad 214 specifically mayinclude one or more slots or drainage holes which may connect to one ormore channels running to an outside of the housing 202, e.g. outletvents on the side closest to the pickup pad 214 (side 206 in the exampleof FIG. 2). A raised bed may also be included to further prevent watersoaking in the pickup pad 214.

The pickup pad 214 may be sized according to the estimated averagelength and width of the type of package 106 the particular UAVreceptacle 102 has been designed to accommodate (e.g., on the order of10 to 12 inches for 5 pound or less average-sized packages). The pickuppad 214 may include one or more sensors to detect a presence of apackage 106 placed thereon. This may occur, for example, where thepackage 106 is a specialized package used for drone deliveries to bemore durable and reusable (or just a regular box that is still intendedto be reused/recycled), and/or where the user intends to send its ownpackage 106 to another destination that is facilitated by the deliveryentity. In yet another alternative example where the user is sending itsown package 106, the package 106 may instead be placed within thehousing 202 on the reception tray. Combined with that, the user maynotify the delivery entity (e.g., via an app of a user device) of thepickup, make payment or arrange for payment, etc., so that the UAVreceptacle 102 may also be used to source deliveries via drone 104 toother destinations.

Returning to the pickup pad 214 in particular (which may also be used tosource deliveries, though this is not secure, and thus may simply beused to return used packages 106 after their contents are removed), toavoid false positives, a controller in the housing 202 may delayalerting a pickup system (whether the delivery entity that hadfacilitated sending the package 106 or some third party recyclingservice, etc.) until it receives an additional input identifying thepackage 106 for pickup. This may include a user input that thecontroller either awaits or that it prompts from the user. Thus, theuser may input a command via the security access mechanisms 216 and/orsome other user interface of the housing 202 or the user's user device(via an app, for example). Thereafter, a pickup request may be signaledfrom the user's network to the appropriate retrieving party (whether thedelivery entity or third party, etc.). The signal may be generated fromthe app of the user's device, from the controller of the UAV receptacle102, some combination of both, etc.

The housing 202 may further include a solar array 218 to provide powerto one or more batteries of the housing 202 (e.g., to provide power toactuators associated with the doors 212 a, 212 b, the controller, etc.).The solar array 218 may be generally flush (e.g., integrated with) thesurface of the top 201 or raised therefrom (e.g., for customizabledirecting towards an ideal azimuth and elevation for maximizingharvesting of solar energy). The exact location/area on the top 201 (orseparate from the housing 202 and coupled thereto by one or more cablesand/or one or more arms, for example) may vary and is not limited to thelocation/area illustrated in FIG. 2 (or FIGS. 3D, 4, 5A, 5D).

A cross section is also illustrated in FIG. 2 extending horizontallyacross the housing 202 from a center of the side 210 where the doors 212a, 212 b are located to the rear side 208 of the housing 202 (rearreferring here simply to the side 208 that is opposite the side with thedoors 212 a, 212 b). The cross section is illustrated in FIG. 4 todetail some of the contents of the interior of the housing 202.

FIG. 3A illustrates a side view of the UAV receptacle 102 according toaspects of the present disclosure. In particular, FIG. 3A illustratesthe side 206 of the housing 202. The side 206 may be one of the sidesadjacent to the side 210 having doors 212 a and 212 b (e.g., from a topview of the housing 202, the side being to the right of the side 210,though it may be the other side instead).

The side 206 as illustrated includes the one or more security accessmechanisms 216, illustrated as a keypad in this example. These may beincluded to enable a user of the UAV receptacle 102 to access one ormore packages 106 stored securely within the housing 202 according toembodiments of the present disclosure. Though illustrated as beingsimply a keypad, the one or more security access mechanisms 216 may be amanual keypad, a touchscreen keypad, a combination of a keypad and avoice system, and/or a display (whether touchscreen or not), etc.

FIG. 3B is a block diagram of a side view of the UAV receptacle 102according to aspects of the present disclosure. FIG. 3B illustrates theside 210 that includes the doors 212 a, 212 b. Adjacent the side 210 arethe sides 206 discussed above with respect to FIG. 3A and the side 220.

The doors 212 a, 212 b of side 210 may define a full area of the side210. Alternatively, the doors 212 a, 212 b may occupy an area that isless than a full width and height of the side 210, albeit still sizedsufficiently to accommodate a package 106 having target dimensions. Asnoted with respect to FIG. 2, though the doors 212 a, 212 b areillustrated as being separated along a vertical axis extending from thetop 201 to the bottom 204 of the housing 202, the doors 212 a, 212 b mayassume alternative configurations. Some alternatives include beingseparated along a horizontal axis extending from the sides 206 to 220instead, and/or have more or fewer total doors. For example, inembodiments with fewer doors, a single door 212 may be used that swingsout from the housing 202 when opening (whether hinged at the interfacewith the top 201, or at the interface with the bottom 204, or one of thesides 206, 220). As another example, in embodiments with more doors,there may be three doors, four doors, or more that open out to allow thereception tray to extend out to a reception position and back to astorage position within the housing 202, etc.

FIG. 3C is a block diagram of a bottom view of the UAV receptacle 102according to aspects of the present disclosure. FIG. 3B illustrates thebottom 204 of the housing 202. The bottom 204 may include a recess 221sized to accommodate the post 103 introduced with respect to FIG. 1above. The recess 221 may include a securing mechanism, such as a lock,a bolt, an adhesive, etc. to couple the housing 202 to the post 103 in amanner that prevents theft of the housing 202. In alternativeembodiments, the recess 221 may not be physically recessed from the restof the surface of the bottom 204, but instead be a defined region towhich a post 103 may couple or be permanently attached.

Turning now to FIG. 3D, a block diagram is illustrated of a top view ofthe UAV receptacle 102 according to aspects of the present disclosure.FIG. 3D illustrates the top 201 of the housing 202.

As noted with respect to FIG. 2, the top 201 may include regions definedfor the pickup pad 214 and the solar array 218. As illustrated in FIG.3D, the doors 212 a, 212 b are in a slightly open position, representingeither the doors 212 a, 212 b actuating to an open position for thereception tray within the housing 202 to actuate to a reception positionor actuating to a shut position for the reception tray in a storageposition within the housing 202.

FIG. 4 is a block diagram of a cross-sectional view of the UAVreceptacle 102 according to aspects of the present disclosure. Inparticular, FIG. 4 provides a cross-sectional view of the housing 202introduced in FIG. 2, extending from the side 210 having the doors 212a, 212 b toward the rear side 208 (that is opposite the side 210).Although illustrating the embodiment with two doors 212 a, 212 b, thecross-section shown in FIG. 4 may be generally the same for embodimentswith other door configurations, e.g. a single door (whether attached tothe reception tray or in an actuated relationship with the housing 202)or multiple doors. FIG. 4 also illustrates a reception tray 222 onmounts 228 (e.g., roller mounts).

The cross-sectional view shown in FIG. 4 is from the perspective view ofFIG. 2 along the axis drawn in FIG. 2 (and labeled “FIG. 4”). Thus, inFIG. 4, half of the pickup pad 214 is illustrated in the cut-out fromthe top 201 followed by the solar array 218 extending towards the farside of the housing 202. Further, half of the recess 221 on the bottom204 is illustrated in the cutout of FIG. 4 as well. In the example ofFIG. 4, the doors 212 a, 212 b are in the open position and thereception tray 222 is in the receipt position (i.e., fully extended outof the housing 202). In this configuration, the UAV receptacle 102 isready to receive a package 106.

The reception tray 222 may be constructed from a mesh material 224 thathas a porosity sufficient to allow precipitation to at least dripthrough after contact, while bound together closely enough to supportreceipt of a package 106 (e.g., the weight of the package 106, bothstanding weight as well as the added force of a drop of the package 106from some approximate height from the drone 104, such as in the range of16 inches to 32 inches to name just one example—this could be in therange of 40-60 pounds, though other ranges are also possible andenvisioned both greater and less than that). The mesh material 224 maybe composed of any of a variety of materials, including some form ofmetal such as steel, aluminum, or some other metal/alloy, carbon fiber,polymer (e.g., plastics), etc.

The reception tray 222 may also include a sensor 226 that detects thepresence of a package 106. For example, the sensor 226 may include aweight sensor, a force sensor, a capacitive sensor, an image sensor,some combination thereof, or other sensor that detects presence of apackage 106. The sensor 226 may be a pad placed on top of the meshmaterial 224 and adhered thereto (e.g., via adhesive or some mechanicalconnection) or be integrated with the mesh material 224 (e.g., woven orplaced between layers of the mesh material 224 to name just a fewexamples).

There are several alternatives to the configuration of the receptiontray 222. In addition to the example illustrated in FIG. 4, thereception tray 222 may further include small walls on sides of thereception tray 222 so as to assist in preventing packages 106 dropped tothe reception tray 222 from bouncing off upon drop from the drone 104.Such walls may be sized to be some percentage of the overall height ofthe housing 202, for example less than half the height (e.g., 4 inchesas just one non-limiting example), to almost the full height from bottom204 to top 201. Alternatively or in addition, the reception tray 222 mayhave different configurations than the flat configuration illustrated inFIG. 4. For example, the reception tray 222 may itself have anindentation such that the outer edges of the reception tray 222, in theorientation of the housing 202, are further away from the bottom 204than a central, lowered portion of the reception tray 222. The loweredportion in such embodiments may be sized to be approximately flat forsome minimum length and width to facilitate better receipt of packages106 upon drop from a drone 104, e.g. corresponding to the length andwidth of the sensor 226, with sloped portions on each of the sides ofthe reception tray 222 up towards the higher outer edges. This may beinstead of the walls or in combination therewith.

Returning to the sensor 226, it may be battery-operated independent ofother aspects of the housing 202 or alternatively be wired or wirelessly(for power) connected to other components of the housing 202 (e.g.,through the mesh material 224 and via the mounts 228). Further, theoutput of the sensor 226 may be conveyed to other components of thehousing 202 via wired or wireless connection(s). For example, once thesensor 226 is triggered upon sensing a package 106, the sensor 226 mayassert what is referred to herein as a detection signal (which mayassume the form of one or more signals of a length appropriate toidentify the detection, ranging from assertion of a single bit to somestring of bits identifying information output from the sensor 226without departing from the scope of the present disclosure).

Other components within the housing 202 include a controller 230 and apower source 232. Although illustrated as both being located on the sameside of the housing 202, they may be located on different sides thaneach other (including attached to the interior side of the top 201 or,if of a sufficiently low profile, laid out below the traversal region ofthe reception tray 222). The controller 230 may include at least onetransceiver, at least one processor, and at least one memory as will bediscussed in more detail below with respect to FIG. 6. The controller230 may communicate with the different sensors associated with thehousing 202, including for example associated with the sensor 226 of thereception tray 222, a sensor associated with the pickup pad 214, thesecurity access mechanisms 216, and any other sensors of the housing202. Further, the controller 230 may be in communication with the solararray 218 to send commands thereto and receive data therefrom.

According to embodiments of the present disclosure, the controller 230,upon a proximity signal being asserted in response to a drone 104 comingwithin a predetermined range of the UAV receptacle 102 (e.g., based ondetection/communication with the drone 104 by the transceiver of thecontroller 230), sends a command to actuate the doors 212 a, 212 b tothe open position, and sends a command to actuate the reception tray 222from a storage position to a reception position. Where the door 212 ispart of the reception tray 222, then the commands may be a singlecommand to actuate the reception tray 222. The controller 230, uponreceipt of a detection signal from the sensor 226, may command thereception tray 222 to actuate and retract back to the storage positionand also command the doors 212 a, 212 b to actuate to the shut position(which may be accomplished by retracting the reception tray 222 wherethe door is part of the reception tray 222).

Further according to embodiments of the present disclosure, thecontroller 230 (via the transceiver thereof), may notify one or moresubscribing users of the UAV receptacle 102 of the receipt of a package106 upon closing the door 212 (e.g., doors 212 a, 212 b in the exampleof FIG. 2). This notification may again be performed via the transceiverof the controller 230. This is addressed in more detail with respect toFIG. 6 below. Further, alternatively or in addition, the housing 202 mayinclude one or more visual indicators (e.g., lights, screens, etc.) tophysically alert a user of the presence of a package 106 therein.

The power source 232 may be any available power source that can providesufficient power to the components of the housing 202 over a desiredperiod of time. For example, the power source 232 may be a collection ofone or more rechargeable batteries (e.g., lithium batteries, wet-cellbatteries, dry-cell batteries, etc.). The power source 232 may, incommunication with the controller 230 and the solar array 218,periodically receive an inflow of power generated from the solar array218 when the solar array 218 is active (either from solar input beingavailable, the controller 230 allowing charging to occur, or somecombination thereof). The power source 232 may also be or include amains power source that may include components to convert an alternatingcurrent voltage input (e.g., plugged into a socket from a user'sbuilding) into a direct current voltage regulated for use by thecomponents of the housing 202.

In some embodiments, the power source 232 may actually include two ormore distinct power sources (e.g., multiple cell packs as just onephrase to describe the various types of power supplies available) thatoperate in cooperation under the controller 230 to power the actuators,sensors, and other components of the housing 202. For example, a firstcell pack of the power supply 232 may power the components of thehousing 202. The controller 230 may monitor the status of the powersupply 232 and detect when the first cell pack falls below a supplythreshold. In response, the controller 230 may direct power to besupplied instead from a second cell pack (which may have been replacedor recharged). After the switch, the first cell pack may beginrecharging or be replaced.

The controller 230 may signal the switch occurring to the subscribinguser (e.g., via an app on the user's device) or may wait to signal theuser unless and until all of the cells of the power supply 232 (ormultiple power supplies 232) fall below a threshold that will requirethe user's attention to prevent loss of operation of the UAV receptacle102. In embodiments where the power supply 232 does not have the abilityto switch between multiple sources of power, the controller 232 maysignal low power to the user when the power falls below a threshold, incase the user needs to intervene to replace one or more batteries of thepower supply 232 to ensure continued operation of the UAV receptacle102.

As noted above, the UAV receptacle 102 may grant access to a receivedpackage 106 by opening the doors 212 a, 212 b, extending the receptiontray 222 to the receipt position again, and allowing a user to removethe package 106. This may be done in response to a command entered viathe one or more security access mechanisms 216 or via an app on theuser's device (e.g., received via the transceiver of the controller230). The reception tray 222 may begin retracting to the storageposition in response to a change detection by the sensor 226, a commandfrom the one or more security access mechanisms 216, and/or a commandfrom an app on the user's device to name just a few examples. Uponreaching the storage position, the doors 212 a, 212 b may automaticallyclose (or, in embodiments where attached to the reception tray 222,close by virtue of the reception tray 222 retracting).

In other embodiments (or in addition to the above), the housing 202 mayfurther include an access door. FIG. 5A is a block diagram of a frontperspective view of an exemplary UAV receptacle 102 according to aspectsof the present disclosure. The housing illustrated 202 is similar tothose discussed with respect to FIGS. 2-4 above, with the modificationsas noted below.

As illustrated, the housing 202 may further include an access door 223in one of the sides of the housing 202. As illustrated in FIG. 5A, theaccess door 223 is on the side 220 that is adjacent to the side 210 withthe doors 212 a, 212 b. This is exemplary only. The access door 223 maybe placed, where included, on any of the sides besides the side 210 thathas the access door 212. The side on which the access door 223 islocated may not include the controller 230 and/or the power supply 232,while in other embodiments the side with the access door 223 may includeone or both where that particular side is left with a bezel (e.g., wherethe access door 223 does not occupy the entire area of the particularside).

In other embodiments, the access door 223 may define the entire side (inthis example, side 220). Alternatively, the access door may be definedon the side that includes the one or more security access mechanisms216. Therefore, the one or more security access mechanisms 216 mayinteract via the controller 230 (or independent of the controller 230)to control a lock on the interior of the housing 202 to secure theaccess door 223.

In some embodiments, the access door 223 may be sized on the side (e.g.,side 220) to permit both manual user access as well as provide aninterface between the housing 202 and an expansion container (e.g., byswinging up to open via hinges near the top 201 of the housing 202 toreleasably connect to a receiving unit in the expansion container, or bycomplete removal in configurations when connected to the expansioncontainer, etc.).

FIG. 5B is a block diagram of a front perspective view of an exemplaryexpansion container 502 a for UAV receptacle 102 according to aspects ofthe present disclosure. The expansion container 502 a is designed to bean optional add-on to the UAV receptacle 102, for example for use bythose who are heavy users of drone delivery (e.g., multiple packagesexpected on a given day). In other examples, the expansion container 502a may be integrally manufactured with the UAV receptacle 102.

The expansion container 502 a illustrated in FIG. 5B includes a side504, another side 506, top 508, a bottom 510, front 509, and a rear(from the view of the illustration in FIG. 5B). As illustrated, the side504 is the side designed to interface with the housing 202 (such as theone illustrated in FIG. 5A). For example, the side 504 includes anopening 512 that has at least the same area as that of the access door223 of the housing 202, and one or more couplers 514 to releasablyconnect to the side 220 of the housing 202 (e.g., where the two are notintegrated with each other at manufacture).

From the side 504, the expansion container 502 a may have an interiorportion defining an upper portion 516 that may have a larger length thanheight, as well as an interior portion defining a lower portion 517.Although illustrated as distinct portions, upper portion 516 and lowerportion 517 define an interior of the expansion container 502 a and arecalled out separately herein merely for ease of discussion ofembodiments of the present disclosure.

The side 506 may be the side that is opposite the side 504 thatinterfaces with the housing 202. This side 506 may include a retrievaldoor 520 located along some height for access to at least the lowerportion 517 (and, in some embodiments, the upper portion 516). Theretrieval door 520 may be attached to the side 506 via one or morehinges, slots, etc., so that the retrieval door 520 may allow access tothe interior of the expansion container 502 a as desired. The retrievaldoor 520 may include one or more handles 522. For example, where hingesare located on a side of the retrieval door 520, the handle 522 may belocated toward an opposing side of the retrieval door 520. As anotherexample, where hinges are located at a top or bottom of the retrievaldoor 520, the handle 522 may be located at an opposing bottom or top,respectively, of the retrieval door 520.

In other embodiments, the retrieval door 520 may comprise a rolling orsliding door, e.g. rolling or sliding up from the bottom 510 toward thetop 508. Whatever the embodiment, the retrieval door 520 may be securedin the expansion container 502 a via one or more locks on the interiorof the expansion container 502 a. The locks may be controlled by aphysical key, another keypad, and/or the controller 230 (e.g., with appcontrol of a user device) of the housing 202 where electricallyconnected (such as via the one or more couplers 514).

In use, the housing 202 may further include a box actuator that islocated on an opposing interior surface of the access door 223. Theremay be a single box actuator with a sufficiently slim profile so as tonot interfere with packages 106 while the reception tray 222 is in astorage position, or the box actuator may be multiple box actuators thatoperate in coordination with each other, again with sufficiently slimprofile. When a package 106 is received and the reception tray 222 isback in the storage position, the controller 230 may direct the boxactuator to actuate the package 106 currently on the reception tray 222towards the expansion container 502 a via the opening 512 and into theupper portion 516 (which may include, e.g., rollers or some othermechanism to encourage movement of the package 106 while actuated by thebox actuator in the housing 202, thereby reducing the length that thebox actuator must be).

In embodiments where the reception tray 222 includes sides or a slopedconfiguration to aid preventing bouncing, further mechanisms may beinvolved to facilitate transfer. For example, a side of the receptiontray 222 that is proximal to the side of the housing 202 with the accessdoor 223 may be formed of a pliable material that either extends andcontracts with the movement of the reception tray 222 (such that theside is not present when the reception tray 222 is in the storageposition so the package 106 may move freely towards the upper portion516) or may fold down towards the opening 512 in response to reachingthe storage position or upon application of force from the box actuatoras transferred via the package 106 on the reception tray 222 at thetime.

The box actuator may activate in any one or more of a variety of ways.For example, in embodiments where the expansion container 502 a iscoupled to the housing 202, the controller 230 may maintain a “busy”signal to indicate to any possible future drones 104 that deliverycannot yet be accomplished. Thus, in some embodiments the controller 230may activate the box actuator automatically in response to the receptiontray 222 reaching the storage position with the doors 212 a, 212 bclosing. Once the package 106 is actuated into the upper portion 516 andhas cleared the reception tray 222 (e.g., as noted by a change indetection signal from the sensor 226), the controller 230 may clear the“busy” signal to allow another delivery.

In other embodiments, the controller 230 may wait until an event occursto trigger clearing of the reception tray 222 for another delivery. Forexample, a user may enter a command via an app on the user's device toclear the reception tray 222 (e.g., upon receipt of the notification ofthe delivery of the package 106 via the app). As another example, thecontroller 230 may trigger clearing of the reception tray 222 inresponse to detecting another drone 104 entering the defined range ofthe UAV receptacle 102.

After the package 106 enters the upper portion 516, the package 106 maycontinue its movement towards the lower portion 517, for example by wayof gravity along the length 518 (that extends approximately the sameamount as the length of the post 103 in some examples). In someembodiments, the lower portion 517 is simply an open area in which thepackages 106 may fall and stack on top of each other. In other examples,a dampener may extend from the bottom 510 on the interior of theexpansion container 502 a to dampen the fall of the packages 106 (e.g.,having a weight threshold with a spring effect, a cushion, somecombination thereof, etc.). In some embodiments, the lower portion 517may include an additional sensor to detect the presence of one or morepackages 106 in the expansion container 502 a, which may for example bein communication with the controller 230 to alert the user via the app,and/or with a physical indicator (e.g., light) on the expansioncontainer 502 a.

In some embodiments, a sensor may be used to prevent jamming of thesystem; for example, a light sensor may be used at the top of the lowerportion 517 and/or at the opening 512. If the light sensor remainstriggered after removing a package 106 from the reception tray 222, thecontroller 230 may utilize this information to notify the user via theapp that the UAV receptacle 102 is full and/or notify delivery entitiesthat no additional packages 106 may be received at that time (with asubsequent notification indicating when additional packages 106 mayagain be received).

The expansion container may have other alternative configurations, oneof which is illustrated in FIG. 5C. FIG. 5C provides a block diagram ofa front perspective view of an exemplary expansion container 502 b for aUAV receptacle 102 according to aspects of the present disclosure. Asthere are several similarities between expansion container 502 a andexpansion container 502 b, only those differences between the two willbe discussed.

The primary difference lies in the orientation of the lower portion 517,which instead of being approximately perpendicular to the upper portion516, lies at an obtuse angle thereto. This may aid in providing a moregradual descent for packages 106 when they are actuated off from theupper portion 516. At the bottom 510 of the expansion container 502 b, ablock portion 519 may be included to better orient the packages 106 forpickup after opening the retrieval door 520.

FIG. 5D is a block diagram of a front perspective view of an exemplaryexpansion container coupled to UAV receptacle according to aspects ofthe present disclosure. The combined apparatus 550 is illustrated basedon the exemplary expansion container 502 a introduced in FIG. 5B aboveas just one example for ease of illustration, though other expansioncontainer embodiments may be used instead.

As illustrated, the housing 202 may be coupled to the expansioncontainer 502 a (e.g., via the couplings 514) to form a waterproof seal(e.g., via one or more gaskets, overlapping surfaces, etc.). As notedpreviously, the access door 223 may, in some embodiments, be fullyremoved from the housing 202 when coupling the expansion container 502 athereto. In other embodiments, the access door 223 may swing on one ormore hinges into an extended position and coupled to a receiving end inthe opening 512 of the expansion container 502 a.

Turning now to FIG. 6, a block diagram of a control system 600 of anexemplary UAV receptacle 102 according to aspects of the presentdisclosure is illustrated. In some embodiments, the control system 600includes the controller 103 discussed above. For example, the controlsystem 600 may include a controller 610 (of which controller 103 is anexample), one or more actuators 612, and multiple sensors and otherinputs. These elements may be in direct or indirect communication witheach other via the connection 634, which may illustrate one or morebuses, one or more wired or wireless connections, etc.

Looking at the controller 610 in particular, it may include atransceiver 602, a processor 604, and a memory 606. Although illustratedas generally grouped together, e.g. part of the same physical structureof a controller 610, these components may be instead logically groupedtogether but be in physically distinct enclosures without departing fromthe scope of the present disclosure. As shown, the transceiver 602 mayinclude a variety of different protocol-specific functions (which maycorrespond to distinct transceiver hardware/antenna, different softwareprotocols for shared hardware, or some combination thereof). Forexample, the transceiver 602 may include a global navigation system suchas a global positioning system (GPS). Although identified as GPS, thismay alternatively be some other navigation system, including Galileo,GLONASS, BeiDou, or some other system that enables the controller 610 todetermine geolocation information. The GPS functionality for thetransceiver 602 may aid in unmanned vehicle delivery, for example.

Another function that the transceiver 602 may include is a Bluetoothprotocol (whether Bluetooth or Bluetooth Low Energy). The transceiver602 may utilize the Bluetooth protocol to communicate with other deviceswithin range, for example the user's device (e.g., a cell phone, tablet,smartwatch, etc.) and/or a drone 104. Yet another function may be a nearfield communication (NFC) protocol that uses the transceiver 602 or adedicated transceiver therefor. The NFC protocol may likewise be usedfor communicating with user's device and/or drone 104. For example, NFCmay be used as an unlocking mechanism, e.g. the user activates thefeature in an app on the user device, which is waved within a closeproximity of the transceiver 602 near the housing 202 in order toactivate unlocking of the housing 202.

Yet another function for the transceiver 602 may be a Wi-Fi protocol(e.g., 802.11) with the transceiver being dedicated thereto or shared.For example, the transceiver 602 may utilize Wi-Fi to communicate withdrones 104 when within range (e.g., utilizing ad-hoc variants of the802.11 protocol or via an access point nearby), with the user's device(same, ad-hoc or via access point), or with some remote system such asthe delivery entity (a package delivery entity, a warehouse, etc.) viaan access point. The transceiver 602 could additionally or alternativelyinclude a cellular transceiver (either protocol only or distincttransceiver). The transceiver 602 may, via the cellular transceiver,communicate with the user's device, the drone 104, and/or deliveryentity without requiring additional infrastructure provided by the user(e.g., access points like with Wi-Fi). The above differentprotocols/hardware of the transceiver 602 are exemplary—the transceiver602 may include other additional protocols/hardware in order tofacilitate communication with the user's device, drones 104, and/ordelivery entities that operate the drones 104.

The processor 604 may have various features as a specific-typeprocessor. For example, these may include a central processing unit(CPU), a digital signal processor (DSP), an application-specificintegrated circuit (ASIC), a controller, a field programmable gate array(FPGA) device, another hardware device, a firmware device, or anycombination thereof configured to perform the operations describedherein with reference to the controller 230 introduced above. Theprocessor 604 may also be implemented as a combination of computingdevices, e.g., a combination of a DSP and a microprocessor, a pluralityof microprocessors, one or more microprocessors in conjunction with aDSP core, or any other such configuration. Further, the processor 604may represent a single core or processor, a multi-core processor, and/ormultiple multi-core processors.

The memory 606 may include a cache memory (e.g., a cache memory of theprocessor 302), random access memory (RAM), magnetoresistive RAM (MRAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), flash memory, solid state memorydevice, hard disk drives, other forms of volatile and non-volatilememory, or a combination of different types of memory. In someembodiments, the memory 606 may include a non-transitorycomputer-readable medium. The memory 606 may store instructions 608. Theinstructions 608 may include instructions that, when executed by theprocessor 604, cause the processor 604 to perform operations describedherein with reference to a controller 230 in connection with embodimentsof the present disclosure. The terms “instructions” and “code” mayinclude any type of computer-readable statement(s). For example, theterms “instructions” and “code” may refer to one or more programs,routines, sub-routines, functions, procedures, etc. “Instructions” and“code” may include a single computer-readable statement or manycomputer-readable statements.

The control system 600 may further include the one or more actuators612. For example, the one or more actuators 612 may include one or moredoor actuators 614. For example, each door 212 a, 212 b may have arespective actuator 612 controlled by the controller 610. Where thedoors 212 are integrated with the reception tray 222, this may not beincluded. As another example, the one or more actuators 612 may includeone or more reception tray actuators 616, used under the control ofcontroller 610 to actuate the reception tray 222 (e.g., FIG. 2) into areception position and back to a storage position. As yet anotherexample, the one or more actuators 612 may include one or moreretractable arm actuators 618. These are illustrated in dashed lines inFIG. 6 to illustrate that these actuators 618 may be included only whereit is envisioned that the housing 202 may be coupled to an expansioncontainer 502 (e.g., the 502 a or 502 b examples discussed above).

For any of the above actuators 612, they may take the form of solenoids,electric motors, hydraulic cylinders, pneumatic cylinders, and/or someother combination of motors depending on environment and application.

The control system 600 may include other data sources/inputs/outputscoupled to the controller 610 and, some or all of each other. Forexample, battery sensor 620 may be one or more sensors that operate thestatus of the power source 232. Solar panel 622 may be a sensor and/orcontroller of the solar array 218 introduced above that is incommunication with the controller 610. Tray sensors 624 may include thesensor 226 discussed above with respect to the reception tray 222, andtherefore constitute one or more sensors attached to or integrated withthe mesh material 224. The pad sensors 626 may include one or moresensors to detect a presence of a package 106 placed on a pickup pad 214(e.g., FIG. 2).

The key pad 628 may be an embodiment of the one or more security accessmechanisms 216 (e.g., FIG. 2) discussed above. These may be incommunication with the controller 610 to control the one or more locks632 (or in direct communication with the lock(s) 632) to limit operationof the one or more doors of the housing 202. The control system 600 mayfurther include a user interface 630, for example a screen, one or morelights, trackpad, mouse, etc., and may be a part of the one or moresecurity access mechanisms 216 or be physically and/or logicallydistinct therefrom. The user interface 630 may additionally be used tocontrol the locks 632, actuation of one or more of the doors of thehousing 202, and/or display information such as packages available,costs incurred for package delivery, etc.

FIG. 7 is a block diagram of a user's device 700 in communication withan exemplary UAV receptacle 102 according to aspects of the presentdisclosure. The user's device 700 may be, for example, a cellular phone,a tablet, a laptop, a smartwatch, or some other computing device capableof communicating with the controller 230 of the UAV receptacle 102according to embodiments of the present disclosure. The user's device700 may include a transceiver 702, a processor 704, a memory 706, an app710 (also referred to generically as a “dropbox app” for purposes ofdiscussion), and a user interface (UI) 712. The UI 712 may assume any ofa variety of input and/or output mechanisms, for example a screen, oneor more lights, a trackpad, a mouse, etc. The user's device 700 mayinclude other components that are not illustrated herein so as to focuson aspects of the present disclosure.

The transceiver 702 may include one or more protocol types, for examplea Wi-Fi protocol (e.g., 802.11). For example, the transceiver 702 mayutilize Wi-Fi to communicate with the UAV receptacle 102 and, in someembodiments, with the delivery entity or other centralized managementsystem (for either the delivery entity, the entity providing the UAVreceptacle 102, or both). The transceiver 702 may communicate with theother devices using the Wi-Fi protocol via an access point or directly.The transceiver 702 may additionally or alternatively operate accordingto a Bluetooth protocol (whether Bluetooth or Bluetooth Low Energy) forthe same purposes. The transceiver 702 could additionally oralternatively include a cellular transceiver. The transceiver 702 may,via the cellular transceiver, communicate with the UAV receptacle 102,the drone 104, and/or delivery entity without requiring additionalinfrastructure provided by the user (e.g., access points like withWi-Fi). The above different protocols/hardware of the transceiver 702are exemplary—the transceiver 702 may include other additionalprotocols/hardware in order to facilitate communication.

The processor 704 may have various features as a specific-typeprocessor. For example, these may include a central processing unit(CPU), a digital signal processor (DSP), an application-specificintegrated circuit (ASIC), a controller, a field programmable gate array(FPGA) device, another hardware device, a firmware device, or anycombination thereof configured to perform the operations describedherein with reference to the user's device introduced above. Theprocessor 704 may also be implemented as a combination of computingdevices, e.g., a combination of a DSP and a microprocessor, a pluralityof microprocessors, one or more microprocessors in conjunction with aDSP core, or any other such configuration. Further, the processor 704may represent a single core or processor, a multi-core processor, and/ormultiple multi-core processors.

The memory 706 may include a cache memory (e.g., a cache memory of theprocessor 302), random access memory (RAM), magnetoresistive RAM (MRAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), flash memory, solid state memorydevice, hard disk drives, other forms of volatile and non-volatilememory, or a combination of different types of memory. In someembodiments, the memory 706 may include a non-transitorycomputer-readable medium. The memory 706 may store instructions 708. Theinstructions 708 may include instructions that, when executed by theprocessor 704, cause the processor 704 to perform operations describedherein with reference to a user's device in connection with embodimentsof the present disclosure.

According to embodiments of the present disclosure, communication withthe UAV receptacle 102 may be coordinated/controlled via the dropbox app710. The dropbox app 710 may be stored, for example, in the memory 706as at least a subset of the instructions 708, and executed by theprocess 704. After installation of the dropbox app 710, communicationmay be established with an associated UAV receptacle 102 (e.g., set upat installation by the user). When a delivery is made to the UAVreceptacle 102, the controller 230 of the UAV receptacle 102 maytransmit a notification to the user's device 700, which is received andprocessed by the dropbox app 710. For example, the dropbox app 710 maycause a notification to be displayed via the UI 712 (e.g., a visualnotification and/or audible alert).

The user may use the dropbox app 710 via the UI 712 to instruct the UAVreceptacle 102 to unlock and/or open/close the reception tray 222.Further, the user may use the dropbox app 710 to cause the receivedpackage 106 to be pushed to an expansion container 502 in embodimentswhere that is included and coupled to the housing 202 of the UAVreceptacle 102. The user may additionally use the dropbox app 710 tocommunicate with the delivery entity and/or provider of the UAVreceptacle 102 (e.g., which the user is renting or has purchased onlicense to name some examples). For example, the user may initiatepayment when a package 106 has been delivered or in preparation fordelivery of a package 106 (e.g., where the user has agreed to paymentfor the delivery as opposed to the delivery entity).

Further, the user of the user's device 700 may utilize the dropbox app710 to schedule pickup of an empty package 106 (and/or of a new package106 that has a destination to another user/online retailer/etc.). Thismay operate in coordination with a sensor that detects the presence ofthe package 106 on the pickup pad 214 prior to pickup being scheduledwith the entity providing the drone 104. As noted previously, to avoidfalse positives, the controller 230 in the housing 202 may delayalerting a pickup system (whether the delivery entity that hadfacilitated sending the package 106 or some third party recyclingservice, etc.) until it receives an additional input identifying thepackage 106 for pickup which is entered via the dropbox app 710.Thereafter, a pickup request may be signaled from the user's network tothe appropriate retrieving party (whether the delivery entity or thirdparty, etc.). The signal may be generated from the dropbox app 710, fromthe controller 230, some combination of both, etc.

FIG. 8 is a block diagram of a server 800 in communication with anexemplary UAV receptacle 102 and a user's device 700 according toaspects of the present disclosure. The server 800 may include atransceiver 802, a processor 804, a memory 806, and a billing database810. The server 800 may include other components that are notillustrated herein so as to focus on aspects of the present disclosure.

The transceiver 802 may include one or more protocol types, for examplea Wi-Fi protocol (e.g., 802.11) as discussed above. For example, thetransceiver 702 may utilize Wi-Fi to communicate with the UAV receptacle102 and, in some embodiments, with the user's device 700. Thetransceiver 802 may include other additional protocols/hardware in orderto facilitate communication, such as any of the examples provided aboveor other available protocols/hardware that enable communication to occurin furtherance of embodiments of the present disclosure.

The processor 804 may have various features as a specific-typeprocessor. For example, these may include a central processing unit(CPU), a digital signal processor (DSP), an application-specificintegrated circuit (ASIC), a controller, a field programmable gate array(FPGA) device, another hardware device, a firmware device, or anycombination thereof configured to perform the operations describedherein with reference to the user's device introduced above. Theprocessor 804 may also be implemented as a combination of computingdevices, e.g., a combination of a DSP and a microprocessor, a pluralityof microprocessors, one or more microprocessors in conjunction with aDSP core, or any other such configuration. Further, the processor 804may represent a single core or processor, a multi-core processor, and/ormultiple multi-core processors.

The memory 806 may include a cache memory (e.g., a cache memory of theprocessor 302), random access memory (RAM), magnetoresistive RAM (MRAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), flash memory, solid state memorydevice, hard disk drives, other forms of volatile and non-volatilememory, or a combination of different types of memory. In someembodiments, the memory 806 may include a non-transitorycomputer-readable medium. The memory 806 may store instructions 808. Theinstructions 808 may include instructions that, when executed by theprocessor 804, cause the processor 804 to perform operations describedherein with reference to a management or control server in connectionwith embodiments of the present disclosure.

For example, the server 800 may include the billing database 810.According to embodiments of the present disclosure, the server 800 maybe operated by the entity responsible for providing the UAV receptacle102, and may be separate/distinct from the delivery entity (such as anonline retailer). Thereby, the entity providing the server 800 and UAVreceptacle 102 may facilitate drone deliveries according to embodimentsof the present disclosure. In some examples, the delivery entity assumesresponsibility for payment of services. For example, each time that adelivery is scheduled and/or completed, the server 800 may receive anotification from the delivery entity and/or the UAV receptacle 102. Inresponse, the billing database 810 may be accessed to generate a billfor the use, either each time a use occurs, on a periodic basis that istracked by the billing database (e.g., monthly), or to track a prepaidnumber of deliveries to name just a few examples.

In other examples, the user of the user's device 700 may have agreed toresponsibility for payment of service via the UAV receptacle 102 and thecorresponding dropbox app 710. In such scenarios, the same options mayapply—either each time a delivery is scheduled or completed, or on aperiodic basis, the server 800 may generate a bill based on theinformation stored in the billing database 810 and sent to acorresponding address for the user (e.g., an email address, a physicaladdress, the dropbox app 710, etc.).

Turning now to FIG. 9, a flow diagram is illustrated of a method 900 foroperating an exemplary UAV receptacle 102 according to aspects of thepresent disclosure. In an embodiment, the method 900 may be implementedby one or more processors of the controller 230 of the UAV receptacle102, executing computer-readable instructions to perform the functionsdescribed herein. It is understood that additional steps can be providedbefore, during, and after the steps of method 900, and that some of thesteps described can be replaced or eliminated for other embodiments ofthe method 900.

At block 902, the controller 230 determines whether the UAV receptacle102 is available to receive a package 106.

At decision block 904, if the UAV receptacle 102 is not available, thenthe method 900 proceeds to block 906. For example, if a package 106 iscurrently in the reception tray 222, then the controller 230 is notavailable for receipt of a new package 106.

At block 906, the controller 230 asserts a “busy” signal, which may betransmitted to the delivery entity, the user's device 700, and/or adrone 104 that may come within a proximity of the UAV receptacle 102.Thus, drones 104 may be prevented from attempting delivery while thisbusy signal is asserted/on record with the delivery entity/etc.

At decision block 908, if the UAV receptacle 102's housing 202 iscoupled with an expansion container 502 (e.g., as introduced in FIG.5B), then the method 900 proceeds to block 912.

At block 912, the controller 230 activates one or more actuators (e.g.,box actuators discussed above) to push the package 106 currently on thereception tray 222 into the expansion container 502.

At block 914, as a result of the controller 230 pushing the package 106from the reception tray 222, the controller 230 (e.g., because thesensor 226 is no longer detecting presence of a package 106 thereon)clears the busy signal. This may include, for example, transmitting thisclearing to the user's device 700 and the delivery entity so that drones104 may again attempt deliveries to the UAV receptacle 102 whendesired/scheduled.

Returning to decision block 908, if the UAV receptacle 102's housing 202is not coupled with an expansion container 502, then the method 900proceeds to block 916.

At block 916, the busy signal remains asserted until a user retrievesthe package 106 currently on the reception tray 222 from the housing202.

Returning now to decision block 904, if the UAV receptacle 102 isavailable (e.g., no package 106 is currently resting on the receptiontray 222), then the method 900 instead proceeds to block 910.

At block 910, the controller 230 maintains the busy signal in anunasserted state, waiting upon a drone 104 to attempt delivery of apackage 106.

From any of blocks 910, 914, and 916, the method 900 proceeds to block918.

At block 918, the controller 230 detects a drone 104 entering aproximity of the UAV receptacle 102. The proximity may be a predefineddistance from the housing 202 that may be measured based on GPScoordinates of the housing 202 as compared to the approaching drone 104,a time-of-flight measurement for one or more signals between the drone104 and the UAV receptacle 102, or some other measurement or combinationthereof.

At decision block 920, the controller 230 determines whether the drone104 is attempting delivery intended for the UAV receptacle 102. This maybe accomplished, for example, by transmitting a challenge (e.g., a querysignal) to the drone 104 that is now within the proximity. If the drone104 is scheduled to make a delivery to the UAV receptacle 102, then thedrone 104 may provide a first, affirmative response. If, instead, thedrone 104 is targeting a different UAV receptacle 102, then the drone104 may provide a second, negative response.

In yet other embodiments, the delivery entity may have transmitted anotification to the user's device 700, and via the dropbox app 710 tothe UAV receptacle 102, indicating that a delivery has been scheduled.The notification may further include an identifier of the particulardrone 104 that has been scheduled to make the delivery. Therefore, thechallenge discussed above may be a query for the drone 104's identifier,which may be compared against that provided in the notification to makea positive match.

Whatever the approach for confirming whether the drone 104 intendsdelivery for the UAV receptacle 102, if the response is the second,negative response (whether provided as such from the drone 104 itself ordetermined by the controller 230 based on the information obtained fromthe drone 104), then the method 900 proceeds to block 922.

At block 922, the controller 230 continues monitoring for a drone 104 toenter a proximity of the UAV receptacle 102.

Returning to decision block 920, if the response is the first,affirmative response, then the method 900 instead proceeds to block 924.

At block 924, the controller 230 causes the doors 212 a, 212 b (asillustrated in the prior figures; if the door is attached to thereception tray 222, then the method 900 block 924 may be combined withblock 926) to open so as to allow the reception tray 222 an egress path.

At block 926, once the doors 212 a, 212 b are in the open position, thecontroller 230 causes the reception tray 222 to actuate from a storageposition within the housing 202 to a reception position extended throughthe opening made by opening the doors 212 a, 212 b.

At block 928, the sensor 226 detects the presence of a package 106dropped from the drone 104. This may be a detection of the act of thepackage 106 hitting the reception tray 222, the continued weight of thepackage 106 (e.g., a difference in weight), or some other relateddetection that identifies the package 106 as now resting on thereception tray 222.

At block 930, the controller 230 processes the detection from block 928and instructs the actuator(s) for the reception tray 222 to actuate thereception tray 222 from the reception position back to the storageposition. This may be done upon the sensor signal being received, inresponse to a confirmation message between the controller 230 and thedrone 104 (e.g., a signal indicating the presence of the package 106 onthe sensor 226 sent to the drone 104, the drone 104 confirming from itsend that it released the package 106, etc.).

At block 932, the controller 230 instructs the actuator(s) for the doors212 a, 212 b to actuate the doors 212 a, 212 b to the closed position(which may be combined with block 930 where the door is attached to thereception tray 222 in such embodiments).

At block 934, the controller 230 confirms receipt of the package 106 tothe management server 800 and/or to one or more servers of the deliveryentity that had sent the drone 104.

At block 936, the controller 230 notifies a user's device 700 associatedwith the user of the UAV receptacle 102, for example the dropbox app710, of the receipt of the package 106.

At block 938, the controller 230 receives a command to unlock the UAVreceptacle 102. This command may be received, for example, via thetransceiver 602 of the controller 230 from the dropbox app 710 based ona command from a user entered via the UI 712. As another example, thecommand may be received from an input entered via the one or moresecurity access mechanisms 216, as discussed above.

At block 940, the controller 230 unlocks the UAV receptacle 102 inresponse to the command received at block 938, thereby allowing accessto the package 106 stored therein. In some embodiments, this unlockingmay be of an access door 223 in the housing 202; in other embodiments,it may be unlocking and causing the reception tray 222 to extend out andback in for retrieval thereby; in yet other embodiments, this may beunlocking of the retrieval door 520 where an expansion container 520 isin use.

The method 900 may continue as laid out above for additional packages.As a result of the elements discussed above, embodiments of the presentdisclosure improve upon the delivery and protection of packages, bothfrom theft and from inclement weather.

FIG. 10 is a flow diagram of an exemplary method 1000 of UAV receptacledelivery from a user device 700 perspective according to aspects of thepresent disclosure. In an embodiment, the method 1000 may be implementedby the dropbox app 710 via one or more processors 704 of the user'sdevice 700, executing computer-readable instructions to perform thefunctions described herein. It is understood that additional steps canbe provided before, during, and after the steps of method 1000, and thatsome of the steps described can be replaced or eliminated for otherembodiments of the method 1000.

At block 1002, the dropbox app 710 receives notification of the UAVreceptacle 102 receiving a package 106.

At decision block 1004, if the UAV receptacle 102's housing 202 is notcoupled to an expansion container 502, then the method 1000 proceeds todecision block 1006.

At decision block 1006, if the user enters an unlock command via the UE712 in the dropbox app 710, then the method proceeds to block 1008.

At block 1008, the dropbox app 710 causes an unlock command to be sentto the UAV receptacle 102 via the transceiver 702.

If instead, at decision block 1006, the user does not enter an unlockcommand, and there is no expansion container 502 at that time, then themethod 1000 returns to decision block 1006 in a holding pattern until acommand to unlock is received. That command may be received via the UI712 of the user's device 700, or from an entry via the one or moresecurity access mechanisms 216 at the housing 202, which may be passedon the dropbox app 710 as a notification.

Returning now to decision block 1004, if the UAV receptacle 102'shousing 202 is coupled to an expansion container 502, then the method1000 proceeds to decision block 1010.

At decision block 1010, if the dropbox app 710 receives an unlockcommand via the user interface 712, then the method 1000 proceeds toblock 1008.

At block 1008, the dropbox app 710 causes an unlock command to be sentto the UAV receptacle 102 via the transceiver 702. In embodiments wherethe unlock command is entered via the one or more security accessmechanisms 216 at the housing 202, then the method 1000 may skip blocks1010 and 1008 and proceed to block 1014.

Returning to decision block 1010, if a command to unlock has not beenreceived, then the method 1000 may proceed to block 1012.

At block 1012, a command may be sent from the dropbox app 710, via thetransceiver 702, to the controller 230 to cause the controller 230 toactuate the box actuator and push the package 106 into the expansioncontainer 502.

From either block 1012 or block 1008, the method 1000 then proceeds toblock 1014, where the dropbox app 710 remains in standby mode untilfurther notifications are received from the UAV receptacle 102, thedelivery entity, and/or some other entity relating to delivery ofpackages 106.

FIG. 11 is a flow diagram of an exemplary method 1100 of accounting foran exemplary UAV delivery according to aspects of the presentdisclosure. In an embodiment, the method 1100 may be implemented by theserver 800, executing computer-readable instructions to perform thefunctions described herein. It is understood that additional steps canbe provided before, during, and after the steps of method 1100, and thatsome of the steps described can be replaced or eliminated for otherembodiments of the method 1100.

At block 1102, the server 800 receives a notification (e.g., viatransceiver 802) of a request to deliver a package to a given UAVreceptacle 102 associated with a user. This may be updated in a recordin the billing database 810 and/or another tracking database.

At block 1104, the server 800 receives a confirmation of delivery of thepackage 106 associated with the notification of block 1102. Thisconfirmation may be received from the drone 104 that made the delivery,the UAV receptacle 102 that received the delivery, or some combinationthereof.

At decision block 1106, if the delivery entity has agreed to be billed,or is assigned to be the billed party by some other mechanism (includingby default), then the method 1100 proceeds to block 1108.

At block 1108, the server 800 generates the bill directed to thedelivery entity. The bill may be generated for the use on a per-usebasis. In other examples, this may occur on a periodic basis that istracked by the billing database 810 (e.g., monthly), or on a prepaidnumber of deliveries to name just a few examples.

Returning to decision block 1106, if the user associated with the UAVreceptacle 102 has agreed to be billed, or is assigned to be the billedparty by some other mechanism (including by default), then the method1100 proceeds to block 1110.

At block 1110, the server 800 generates the bill directed to the userassociated with the UAV receptacle 102. The bill may be generatedaccording to one of the examples laid out above, for example.

From either block 1108 or block 1110, the method 1100 proceeds to block1112.

At block 1112, the server 800 transmits the bill generated to theappropriate entity, whether the delivery entity per block 1108 or theuser per block 1110.

At block 1114, the server 800 receives payment in response to the billtransmitted at block 1112 (e.g., after an appropriate passage of time,etc.).

In some embodiments, the computing system is programmable and isprogrammed to execute processes including the processes of methods 900,1000, and/or 1100 discussed herein. Accordingly, it is understood thatany operation of the computing system according to the aspects of thepresent disclosure may be implemented by the computing system usingcorresponding instructions stored on or in a non-transitory computerreadable medium accessible by the processing system. For the purposes ofthis description, a tangible computer-usable or computer-readable mediumcan be any apparatus that can store the program for use by or inconnection with the instruction execution system, apparatus, or device.The medium may include for example non-volatile memory includingmagnetic storage, solid-state storage, optical storage, cache memory,and Random Access Memory (RAM).

The foregoing outlines features of several embodiments so that thoseskilled in the art may better understand the aspects of the presentdisclosure. Those skilled in the art should appreciate that they mayreadily use the present disclosure as a basis for designing or modifyingother processes and structures for carrying out the same purposes and/orachieving the same advantages of the embodiments introduced herein.Those skilled in the art should also realize that such equivalentconstructions do not depart from the spirit and scope of the presentdisclosure, and that they may make various changes, substitutions, andalterations herein without departing from the spirit and scope of thepresent disclosure.

What is claimed is:
 1. An unmanned vehicle delivery receiving apparatus,comprising: a door defining at least a portion of a side of a housing ofthe unmanned vehicle delivery receiving apparatus, the door configuredto form a water-tight seal when shut; a reception tray within thehousing that comprises a mesh base and a sensor configured to detectplacement of a package on the reception tray as the reception tray isextended exterior to the housing; a transceiver configured tocommunicate with an unmanned vehicle within a proximity of the housingand assert a proximity signal in response to detecting the unmannedvehicle; and a controller configured to receive the proximity signaland, in response to the proximity signal: actuate the door from a shutposition to an open position; actuate the reception tray from a storageposition within the housing to a reception position extended exterior tothe housing through an opening in the housing created from the door inthe open position; actuate the reception tray from the receptionposition to the storage position in response to detecting receipt of adelivery package from the unmanned vehicle via the sensor asserting adetection signal; and actuate the door from the open position to theshut position.
 2. The unmanned vehicle delivery receiving apparatus ofclaim 1, further comprising: a pickup pad in a recess of an upperportion of the housing, the pickup pad sized to hold a box for pickupfrom a retrieving unmanned vehicle, wherein a pickup signal is assertedin response to placement of the box for pickup on the pickup pad.
 3. Theunmanned vehicle delivery receiving apparatus of claim 1, wherein: thereception tray and the door are combined together such that an actuatorcoupled to the reception tray actuates the reception tray and the door,and the unmanned vehicle delivery receiving apparatus further comprises:a solar panel attached to an upper portion of the housing and configuredto provide power to a battery within the housing, wherein the battery isconfigured to supply power to the actuator coupled to the receptiontray, actuators coupled to the sensor and the transceiver, and thecontroller.
 4. The unmanned vehicle delivery receiving apparatus ofclaim 1, further comprising: an expansion door defining at least aportion of a different side of the housing than the door, the expansiondoor configured to form a water-tight seal when shut and securely engagewith an expansion reception box when open; and a retractable arm withinthe housing comprising a proximal end attached to an interior surface ofthe housing and a distal end configured to: engage with a packagesurface of the package to push the package into the expansion receptionbox when engaged with the expansion reception box; and remain retractedwithin the housing when the expansion door is shut.
 5. The unmannedvehicle delivery receiving apparatus of claim 1, wherein the controlleris further configured to: transmit, via the transceiver, a receiptsignal to a management server in response to actuating the door from theopen position to the shut position and the detection signal remainingasserted, the receipt signal triggering a notification from themanagement server to a user device associated with a user of theunmanned vehicle delivery receiving apparatus.
 6. The unmanned vehicledelivery receiving apparatus of claim 1, further comprising: a lockingmechanism configured to maintain the door in the shut position andunlock in response to the controller receiving the proximity signal orin response to receiving a user input that matches a requiredcredential.
 7. The unmanned vehicle delivery receiving apparatus ofclaim 6, wherein the controller, in response to the locking mechanismunlocking in response to receiving the user input, is further configuredto: actuate the door to the open position; actuate the reception trayfrom the storage position to the reception position with the deliverypackage for retrieval; and actuate the reception tray to the receptionposition and the door to the shut position in response to detecting adeassertion of the detection signal from the sensor.
 8. An apparatuscomprising: a housing comprising a door, the door configured to form awater-tight seal in a shut position; a reception tray maintained in thehousing in a storage position and slidably connected to the housing toextend to a reception position external the housing, the reception traycomprising a mesh base and a reception tray sensor configured to asserta detection signal in response to a delivery; a proximity sensorconfigured to detect an unmanned vehicle that enters a proximity of theapparatus and assert a proximity signal in response thereto; atransceiver configured to communicate with a management server that isseparate from the apparatus in response to detecting receipt of apackage from the unmanned vehicle and assertion of the detection signalby the reception tray sensor; and a controller configured to assert adoor open actuation signal to transition the door from the shut positionto an open position in response to the assertion of the proximitysignal, a tray actuation signal to transition the reception tray to thereception position after the door reaches the open position, and areception signal in response to detecting the receipt of the package andthe assertion of the detection signal.
 9. The apparatus of claim 8,wherein: the transceiver is further configured to communicate achallenge to the unmanned vehicle in response to the proximity signalbeing asserted and receive a response to the challenge from the unmannedvehicle, the response comprising a positive response for a packagedelivery and a negative response for no delivery, and the controller isfurther configured to assert the door open actuation signal based on theresponse being the positive response.
 10. The apparatus of claim 8,wherein: the transceiver is further configured to receive a packagedelivery signal from the unmanned vehicle in response to delivery of thepackage, and the controller is further configured to delay transmittingthe reception signal to the management server until both the detectingthe receipt of the package and receipt of the package delivery signaloccur.
 11. The apparatus of claim 8, wherein the transceiver is furtherconfigured to: transmit a notification to a user device associated with,and separate from, the apparatus in response to the detecting thereceipt of the package.
 12. The apparatus of claim 8, wherein thereception tray and the door are combined together such that an actuatorcoupled to the reception tray actuates the reception tray and the door,and the door open actuation signal and tray actuation signal comprise asingle actuation signal to transition the combined reception tray anddoor to the reception position.
 13. The apparatus of claim 8, furthercomprising: a solar panel attached to the housing and configured toprovide power to a battery associated with the housing; a pickup padlocated in a first recess of an upper portion of the housing; and astand housing located in a second recess of a lower portion of thehousing, the stand housing configured to couple with a stand to supportthe housing above a surface.